Event-driven detection of device presence for layer 3 services using layer 2 discovery information

ABSTRACT

Techniques for detecting presence of a remote device at Layer 2 in response to an indication of an attempt to use the device and without maintaining a Layer 3 connection to the device. The techniques allow reducing power consumption without compromising the device&#39;s availability. A device that pairs with a remote wireless device may establish a Layer 3 connection to the remote device to provide services to a user. The Layer 3 connection and underlying Layer 2 connection (e.g., WI-FI, WI-FI DIRECT™ or BLUETOOTH®) may be terminated when the Layer 3 connection is not actively used. Once use of the remote device is desired, its presence may be detected using a Layer 2 device discovery mechanism and the Layer 2 and Layer 3 connections to the device may be reestablished. Services provided at Layer 3, such as steaming data, may then be performed over the reestablished Layer 3 connection.

BACKGROUND

Many computers today have radios to support wireless communication.Wireless communication is used, for example, to connect to an accesspoint of a network. By associating with the access point, a wirelesscomputer can access devices on the network or on other networksreachable through that network, such as the Internet. As a result, thewireless computer can exchange data with many other devices, enablingmany useful functions.

To enable computers to be configured for association with an accesspoint, it is common for the access points to operate according to astandard. A common standard for devices that connect to access points iscalled WI-FI. This standard was promulgated by the WI-FI Alliance, andis widely used in portable computers. There are multiple versions ofthis standard, but any of them can be used to support connectionsthrough access points.

Wireless communications may also be used to form connections directly toother devices without using an access point. These connections aresometimes called “peer-to-peer”(P2P) connections and may be used, forexample, to allow a computer to connect to a mouse or keyboardwirelessly. More generally, peer-to-peer connections may be used toestablish a group of devices of any type that may communicate withoutrequiring an infrastructure. Wireless communications for these directconnections also have been standardized. A common standard for low datarate wireless communications is called BLUETOOTH®.

In some instances, a wireless computer may concurrently connect to otherdevices through an access point and as part of a group engaging inpeer-to-peer communications. More recently a standard has been proposed,called WI-FI DIRECT™, that enables both an infrastructure connection andcommunication as part of a peer-to-peer group with similar wirelesscommunications. This standard, also published by the WI-FI Alliance,extends the popular WI-FI communications standard forinfrastructure-based communications to support direct connections. Thestandard to implement WI-FI DIRECT™ may be referred to as P2PSpecifications.

WI-FI and WI-FI DIRECT™ are examples of link layer protocols inaccordance with the OSI layered model of network connectivity. Thislayered model defines the different levels at which connectivity isestablished between computing devices that are to communicate over anetwork, with each layer relying on communication being established atthe lower layers. Accordingly, each layer has a protocol defining howcommunication can occur at that layer.

In this layered model, the lowest layer is the physical layer. Inwireless communication, radios that transmit and receive signals thatcarry network communications make up the physical layer. Those radiosoperate according to a protocol so that information transmitted by oneradio may be correctly received by another. The highest layer is theapplication layer. On the computing devices that are to be connected,applications are the sources and/or destinations of informationcommunicated over the network, and those applications communicateaccording to an application layer protocol so that information sent byone application can be interpreted by another application that receivesit.

Other intermediate layers have other protocols. Two such layers areLayer 2, the data link layer, and Layer 3, the network layer. At thedata link layer, a protocol allows information to pass along a linkbetween any two devices. Peer-to-peer protocols, such as WI-FI DIRECT™and BLUETOOTH® are Layer 2 protocols.

A Layer 3 protocol allows devices that are interconnected through anetwork, or possibly multiple intervening devices, to communicate. Acommon Layer 3 protocol is the IP protocol. Under this protocol, devicesare assigned IP addresses that allow devices on the network to processpackets of information addressed with the IP address of a destinationdevice such that the packet is routed to the device.

Protocols operating at Layer 2 and Layer 3 may include discoverymechanisms. For example, for a first device to form a peer-to-peerconnection with a second device, the first device may first “discover”the second device. A Layer 2 protocol may specify communications onedevice can send, and responses other devices may make to thosecommunications, to allow the devices to determine that they are closetogether and both configured to form a Layer 2 connection. A similardiscovery mechanism may exist for devices that may connect over a Layer3 protocol. Though, rather than engage in short range communications,the discovery protocol may allow one device to discover another deviceat any location reachable through Layer 3 communications.

Once the devices determine each other's presence at the discovery phase,they may “pair” by exchanging information. During pairing, the devicesmay exchange information about their capabilities. For example, when apersonal computer pairs with a printer, the computer obtains informationon the printer and its capabilities, and drivers for controlling theprinter are installed on the computer. In addition, the informationexchanged during pairing may allow the devices to reconnect at a latertime without repeating the discovery protocol.

In some instances, a computing device may monitor for other devices,with which it has already paired, to determine whether the devices areconnected to the network. The presence monitoring allows a device tomaintain connections to other available remote devices so that a remotedevice can be accessed without a delay when its use is desired. Forexample, once a personal computer has paired with a printer at Layer 3,the computer may reestablish a Layer 3 connection to the printer at anytime the printer is connected to the Layer 3 network. In this way, thecomputer can stream a document using the Layer 3 connection immediatelyin response to a user command to print the document, without requiring afurther re-discovery and pairing.

SUMMARY

To save power without degrading the availability of network services,techniques are provided for detecting presence of wireless devices thatmay provide services over a Layer 3 network connection, withoutmaintaining a continuous connection to those devices at Layer 3. Byavoiding the need to maintain an active connection at Layer 3,transmissions and receptions that occur in accordance with the Layer 3protocol in order to maintain an active connection are avoided. The needto maintain an underlying connection at Layer 2 may also be avoided.Accordingly, in some embodiments, the techniques may be used in aportable computing device equipped for wireless communication to accessservices over a Layer 3 network in a low power way that extendsoperating time of the computing device between charging a battery of thedevice. Moreover, terminating one or more supporting connections whenthe Layer 3 connection is not actively used permits the wireless devicesto operate in a sleep mode, which may result in saving battery power ofthe devices.

Instead of maintaining a Layer 3 connection to a remote device tomonitor its presence, this connection may be terminated and not resumeduntil occurrence of a trigger event. The trigger event may be anindication of an attempt to use the remote device or other event. Inresponse to the trigger event, device presence may be detected usingdevice discovery functionality provided by a protocol layer other thanthe Layer 3 protocol. In some embodiments, that discovery functionalitymay be provided by a Layer 2 protocol. Device discovery in accordancewith a Layer 2 protocol may be carried out using a Layer 2 discoverymechanism provided by WI-FI DIRECT™, BLUETOOTH® or any other suitableprotocol.

In some embodiments, when a user of a device indicates a desire toaccess a service provided over a Layer 3 connection by another device towhich the Layer 3 connection has been terminated, presence of theanother device may be determined at Layer 2 and the Layer 3 connectionmay be reestablished. The desired service may include, for example,transmitting streaming data, such as to a television or other mediadevice, which may be performed efficiently using a Layer 3 protocol.

The foregoing is a non-limiting summary of the invention, which isdefined by the attached claims.

BRIEF DESCRIPTION OF DRAWINGS

The accompanying drawings are not intended to be drawn to scale. In thedrawings, each identical or nearly identical component that isillustrated in various figures is represented by a like numeral. Forpurposes of clarity, not every component may be labeled in everydrawing. In the drawings:

FIG. 1A is a sketch of an illustrative scenario in which a wirelessconnection at Layer 3 is established between devices that have paired;

FIG. 1B is a sketch of an illustrative scenario in which the wirelessconnection between the devices of FIG. 1A is terminated after the devicepairing;

FIG. 1C is a sketch of an illustrative scenario in which a wirelessdevice monitors for the presence of another device using a Layer 2device discovery mechanism after the connection between the devices isterminated as shown in FIG. 1B;

FIG. 1D is a sketch of an illustrative scenario in which the connectionbetween the devices of FIGS. 1A-1C is reestablished at Layer 3, based onmonitoring device presence using a Layer 2 device discovery mechanism asshown in FIG. 1C;

FIG. 2A is a sketch of an illustrative scenario in which a wirelessconnection is established via WI-FI DIRECT™ by devices that have paired;

FIG. 2B is a sketch of an illustrative scenario in which a device whosepresence is being monitored by one device using a Layer 2 devicediscovery mechanism has concurrently established a Layer 3 connectionwith another device;

FIG. 3 is a block diagram of an illustrative embodiment of componentswithin a computing device adapted to perform device presence monitoringat Layer 2 to support a Layer 3 connection;

FIG. 4A is a sketch of an exemplary user interface displaying a list ofinstalled devices and a list of currently available devices, based ondevice presence monitoring at Layer 2, in accordance with someembodiments;

FIG. 4B is a sketch of an exemplary user interface displaying a list ofinstalled devices;

FIG. 5 is an exemplary embodiment of a method of monitoring devicepresence;

FIG. 6 is an exemplary embodiment of a method of determining devicepresence in response to an indication of an attempt to use of thedevice;

FIG. 7 is a flowchart of an exemplary method of operating exemplarydevices A and B to monitor device presence in accordance with someembodiments;

FIG. 8 is a flowchart of another exemplary method of operating exemplarydevices A and B to determine device presence in accordance with someembodiments;

FIGS. 9A-9D are sketches illustrating an exemplary environment in whichdevice presence may be determined in accordance with some embodiments;and

FIG. 10 is a functional block diagram of an illustrative computingdevice in which embodiments of the invention may be implemented.

DETAILED DESCRIPTION

The inventors have recognized and appreciated that experience of a useremploying a device that obtains Layer 3 network services from otherremote devices may be improved by monitoring presence of the remotedevices without maintaining a Layer 3 connection. For example, apersonal computer or other computing device may monitor presence of awireless printer or other remote device. After a connection, such as anIP connection, to a remote device at Layer 3 is established, subsequentmonitoring of presence of the remote device, while the Layer 3 servicefrom the remote device is not used, may be performed using a Layer 2device discovery mechanism. The monitoring may be conducted in a mannerthat allows reestablishing the IP connection to the remote device, basedon the monitoring, when it is desired to access functionality providedby the remote device.

Initially, a device may connect to one or more remote devices usingconventional Layer 3 connection techniques. For example, it is knownthat for a device to engage in wireless communication with anotherdevice to provide services to a user, the devices may first discovereach other. Once the devices have paired, which involves exchanginginformation about each other's capabilities that is subsequently usedfor communication between the devices, a connection at Layer 3 may beestablished between the devices. Conventional device discoverytechniques operate at Layer 3. For example, device discovery may beperformed in accordance with an IP-based service discovery protocol,such as, for example, Simple Service Discovery Protocol (SSDP), Bonjourand Web Service (WS) Discovery.

One example of a Layer 3 connection that may be established between thedevices following their pairing is an IP connection. Such a connectionuses the Layer 3 Internet Protocol (IP). Though, it should beappreciated that the connection at Layer 3 may be established inaccordance with any other suitable communication protocol, either nowknown or later developed in the future, as embodiments of the inventionare not limited in this respect.

The IP connection may be established between a pair of devices throughan access point, by associating each of the devices with the accesspoint using a WI-FI protocol. Further, depending on a type of thedevice, the devices may form an IP connection established over a directnetwork connection. For example, a personal computer may form a Layer 3connection to a wireless printer over a Layer 2 WI-FI DIRECT™connection.

Regardless of the manner in which devices initially discover and pair,the information obtained by a device in conjunction with its pairingwith a remote device may be stored in a suitable storage location. Thisinformation may be stored such that it is available for later use inestablishing a Layer 3 connection to the remote device without the needfor repeating the discovery and pairing processes. It should beappreciated that a device may store information about multiple devicespaired with that device. For example, more than one personal computermay pair with the same wireless printer that may be then shared by usersof the computers. In some embodiments, the printer may therefore storeinformation on each of the computers obtained as a result of pairingprocess. Alternatively or additionally, the computers each may storeinformation on the printer.

In scenarios in which a device is a computing device, information aboutdevices with which the device has exchanged information for supporting aLayer 3 connection may be displayed on a user interface of the computerin a manner that indicates that the device is available to provide Layer3 services. In some embodiments, the remote devices may be presented ina list of installed devices. The information may be displayed in anysuitable manner—for example, if the remote device is a printer, an icondepicting a printer may be displayed. As another example, theinformation about the device may be displayed indirectly, such as byindicating that a service provided by the remote device is available.Though, it should be appreciated that embodiments of the invention arenot limited with respect to a particular way of providing informationabout devices paired with the computer.

In some embodiments, once the pairing process between any two devices iscomplete, the device may suspend its communication at Layer 3 entirely.For example, the device can disconnect from an access point so that itcan stop receiving and transmitting communications that occur as part ofbeing connected to a network at Layer 3. For instance, after a computerpairs with a wireless printer and it is determined that the IPconnection to the printer is not active, the IP connection between thesedevices may be terminated. Because the IP connection was establishedover an underlying Layer 2 connection, in some embodiments, the devicesmay also disconnect at Layer 2.

Despite the fact that a remote device is no longer connected to anetwork at Layer 3, the device may continue to indicate the availabilityof the remote device for providing services over the Layer 3 network. Insome embodiments, the device may indicate the availability of thoseservices without monitoring whether the remote device remains availableto provide those services. In such an embodiment, if a user indicates aninterest in obtaining services from a remote device, the device may thenattempt to reestablish a connection at Layer 3 to the remote device thatprovides the requested service.

As part of attempting to reestablish the connection, a device maydetermine whether the remote device is available. That determination maybe made based on whether the attempt to form a connection is successful.Alternatively, a determination of the presence of the device may be madeby using a discovery protocol. Though, it is not a requirement that aLayer 3 discovery protocol be used or be the only protocol used. In someembodiments, upon receipt of input indicating reconnection to a remotedevice for Layer 3 services, the device may attempt to discover thedevice using a Layer 2 discovery protocol.

Discovery of the remote device through the Layer 2 discovery protocolmay be used as a condition on attempting to reconnect at Layer 3. Inthis way, Layer 3 communication may only occur if the remote device islocated through Layer 2. Though, in some embodiments, using a Layer 2discovery protocol may be performed first, but a Layer 3 communicationsmay occur to attempt to detect or connect to the remote device if theLayer 2 discovery fails.

In other embodiments, a Layer 2 discovery protocol may be used to obtaininformation indicating the presence of remote devices even before a userindicates a desire to access a service from a remote device. In someembodiments, while the IP connection established between the devices issuspended, presence of the remote devices may be monitored at Layer 2.Any suitable Layer 2 device discovery mechanism may be used for themonitoring. For example, a device discovery mechanism in accordance witha WI-FI DIRECT™ or BLUETOOTH® standard may be utilized. Though, itshould be appreciated that any suitable device discovery mechanism atLayer 2 may be substituted, as embodiments of the invention are notlimited in this respect.

The techniques described herein may be selected to use for devicediscovery based on a type of a device to be discovered. Because theLayer 2 device discovery is a short-range discovery technique, it mayonly be practical to use the described techniques for devices connectedon the same wireless LAN or connected through the same access point.Alternatively or additionally, the Layer 2 device discovery techniquesmay be used for devices that are used when in proximity to each other,such as a computer and a TV in a home environment or a computer and aprinter in an office. It should be appreciated that embodiments of theinvention are not limited with respect to types of devices that canimplement the Layer 2 device discovery techniques as long as suchdevices can communicate at short-range.

In some embodiments, the device discovery mechanism in accordance with aLayer 2 technology may involve sending, by a first device monitoringpresence of a second device, probe requests to the second device forinformation about presence of the second device. If the second device ispresent, it may respond to the requests. The requests may be sent to thesecond device in any suitable manner. In some embodiments, the requestsmay be sent periodically. For instance, if a first device monitorspresence of a second device in accordance with a WI-FI DIRECT™ protocol,the first device may sent a WI-FI Probe Request message to the seconddevice at periodic intervals. Though, it is not a requirement that theprobes be sent at evenly spaced intervals, and such probes may be sentwith any suitable timing. If the second device is present, the devicemay respond to the WI-FI Probe Request message with a WI-FI ProbeResponse message to notify the first device of its presence.

As another example of a discovery mechanism, in some embodiments, thesecond device may send periodic messages in accordance with a Layer 2device discovery protocol, which may be called heartbeat messages, tonotify the first device that the second device is available to the firstdevice. The heartbeat messages may comprise, for example, conventionalLayer 2 broadcast messages. It should be appreciated that the requestsmay be sent other than at periodic time intervals, as embodiments of theinvention are not limited to a particular way of probing a device whosepresence is being monitored in accordance with a Layer 2 devicediscovery mechanism. For example, the requests may be sent at a certaintime.

Monitoring presence of a device at Layer 2 allows presenting informationto a user on availability of the monitored device. Thus, as a specificexample, if a computer monitors presence of a wireless printer that waspreviously paired with the computer, the printer, if determined to bepresent, may be added to a list of devices available to the computer.Accordingly, in this case, on a computing device that distinguishesbetween installed and available devices, a representation of the printer(e.g., an icon or any other visual representation) may be displayed inboth a list of devices installed on the computer and a list of devicesavailable to the computer. The list of available devices may includedevices whose presence has been determined in any suitable way—forexample, the list of available devices may include one or more devicesto which an active IP connection is being maintained.

The list of available devices may be presented on a user interface ofthe computer in any suitable form. Furthermore, as the computer monitorspresence of the printer and other devices paired with the computer, thelist of available devices may be updated to indicate devices currentlyavailable to the computer. Thus, if the computer detects that theprinter is not present, the representation of the printer may be removedfrom the list of available devices. Similarly, a device that isdetermined to be present may be added to the list.

An indication that one or more devices are determined to be available bya monitoring device may be provided in a manner other than displaying arepresentation indicating that the devices are available on a userinterface. For example, once the device is present, an action may betaken that depends on the device being available. Such an action may betaken in response to user input or any other trigger event.

In some embodiments, after a Layer 3 connection to the device issuspended, presence of a device using a Layer 2 device discoverymechanism may not be monitored continuously. Rather, presence of thedevice may be determined upon an occurrence of an event triggering thedetermination, which may comprise any suitable type of event indicatingthat use of the device is desired. For example, after a first device,such as a computer, pairs with a second device, such as a printer, and aLayer 3 connection between the devices is subsequently suspended, nomonitoring of each other's presence by either of the devices may beconducted. However, when a user of the computer indicates (e.g., via auser interface) that use of the printer is desired, this indication mayserve as a trigger for the computer to determine presence of theprinter.

The indication of an attempt to use a remote device may be provided inany suitable way. For example, user input may be received with respectto a representation of the device on a list of installed devices ordisplayed in any other form on a user interface. The trigger may alsocomprise powering up the device. As another example, an indication maybe opening an application or other request to use some functionality ofthe device. Though, it should be appreciated that embodiments of theinvention are not limited to any particular way of indicating an attemptto use the device.

An attempt to use a device over a Layer 3 connection that has beensuspended may result in a determination, based on a Layer 2 devicediscovery mechanism, that the device is not present and therefore is notavailable. A suitable action may be taken when the device is notpresent. For example, if the printer is determined not to be present inresponse to an indication of an attempt of its use, a suitable actionmay be taken. For example, an alternative printer may be suggestedand/or selected by a user. If the alternative printer is installed butits presence has not been determined, the availability of that printermay be determined using a Layer 2 device discovery mechanism inaccordance with some embodiments.

If another device available to the computer is capable of functionalityprovided by the printer determined to be unavailable, an attempt to usethat device may be made. Alternatively or additionally, one or morenotifications may be provided to the user informing the user that thedevice whose use is requested is not available and what other devices,if any, are available to be used instead of the requested device.

Regardless of whether presence of a remote device is determined inresponse to a trigger event, such as an indication of an attempt to usethe device, or as a result of continuously monitoring presence of thedevice in accordance with some embodiments, the Layer 3 connection tothe device may be reestablished if the device is determined to bepresent. Accordingly, the techniques described herein allow, while theconnection to the remote device at Layer 3 has been suspended,determining presence of the device using a Layer 2 device discoverymechanism, and, based on the determination, reestablishing theconnection to the device at Layer 3.

In some embodiments, when a remote device connected via an access pointto an IP network is not actively in use, Layer 3 communications to thisdevice may be suspended—e.g., the device may disconnect from the accesspoint and thus leave the IP network. In response to subsequentdetermining of presence of the remote device at Layer 2, the remotedevice may reconnect at Layer 3. Thus, it may rejoin the IP network byreconnecting to an access point.

Once the connection to the remote device is reestablished, functionalityof the remote device may be accessed. For instance, referring to theabove computer/printer scenario, when the IP connection to the remoteprinter is reestablished, the printer may be used to print documents. Asanother exemplary scenario, a computer may discover and establish an IPconnection with a wireless TV. While the IP connection is terminated, inresponse to receiving an indication of an attempt to stream data to theTV, the computer may determine, using a Layer 2 device discoverymechanism, presence of the TV and, when the TV is determined to bepresent, the IP connection to the TV may be reestablished and data maybe streamed to the TV from the computer.

In some embodiments, the user experience may be improved by reducingpower consumption by the device due to the reduction of an overheadassociated with keeping the Layer 3 connection alive when the connectionis not actively used. Moreover, power that would be required to processmessages exchanged between the devices to maintain the Layer 3connectivity may be saved. Reduced power consumption may be apparent tothe user through longer battery life, for example.

Furthermore, eliminating the requirement to maintain the Layer 3connection may make it unnecessary to maintain an underlying connectionto the device at Layer 2. Thus, power that would otherwise be expendedfor connecting to the Layer 2 network may be saved. The reduction inpower consumption may be particularly useful for devices operating usingbattery as a power source. Further, because the need for communicationsassociated with maintaining a Layer 3 connection is eliminated, thetotal amount of communications is reduced, which can decrease “spectralpollution,” which can interfere with the overall effectiveness ofwireless communications by other devices in the area.

Another improvement resulting from utilizing the described techniquesmay include increasing availability of a device that is capable ofsupporting only a single connection at Layer 2 with another device.Maintaining an IP connection to such device, which expends the singleLayer 2 connection that may be established by the device, may preventits use by other devices, even though the IP connection is used solelyfor monitoring presence of the device and not to use the device'sfunctionality. Accordingly, in such scenarios, terminating the Layer 2connection to a device because it is no longer needed to support thesuspended IP connection while device presence is monitored but thedevice is not in use, may allow the device to engage in communicationwith other devices.

Furthermore, in some scenarios, a device (e.g., a laptop) connected viaan IP connection through an access point to a remote device with whichthe laptop has paired, may monitor presence of the remote device usingan IP-based discovery protocol. However, if the laptop is physicallymoved away from the access point so that it becomes disconnected fromthe access point, a Layer 2-based device discovery mechanism inaccordance with some embodiments may be initiated at the laptop tomonitor presence of the remote device, instead of the IP-based discoveryprotocol. This may improve user experience because the user is notrequired to keep the laptop or other device within the reach of theaccess point for the device to continue being informed about otherremote devices it has paired with. Though, it should be noted that thelaptop may only detect presence of the remote device at Layer 2 if thelaptop and the remote device are located within a short-rangecommunication distance of each other. When the user of the laptopdesires to access the services provided by the remote device over the IPconnection, the user may bring the laptop back to a location that isreachable by the access point so that the IP connection to the accesspoint may be reestablished. Though, the laptop may alternatively form aLayer 3 connection over a direct Layer 2 connection.

The described techniques for device presence monitoring may beadvantageous in scenarios where devices communicating in accordance withthe WI-FI DIRECT™ standard, which is an example of P2P Specifications,support only a single connection at Layer 2 with another device.Maintaining constant IP connectivity over a WI-FI DIRECT™ connectionbetween two such devices may prevent use of those devices by any otherdevice in their vicinity. Accordingly, in such scenarios, terminatingthe Layer 2 connection to a device while device presence is monitoredbut the device is not in use, may allow the device to engage incommunications with other devices.

The forgoing techniques may be used in any suitable environment. FIGS. 1and 2 illustrate environments in which presence of a remote computingdevice may be detected according to some embodiments.

In the example of FIG. 1, an exemplary device, such as computer 102illustrated as a laptop computer, may pair with and establish a Layer 3connection to another device, shown by way of example as a remotewireless printer 104. Though, it should be appreciated that other typesof devices having short-range communication capability may implementtechniques for device discovery at Layer 2 according to embodiments ofthe invention. For example, the computing devices may compriseSmartPhones, PDAs, cameras, TVs, headsets and any other suitable devicesthat may be connected on the same wireless LAN or connected through thesame access point.

In the illustrated exemplary scenario, computer 102 and printer 104 maybe used in a home or office environment where a user 106 may usecomputer 102 to print documents on printer 104. User 106 may interactwith computer 102 to control computer 102 to wirelessly connect withremote devices, such as printer 104.

FIG. 1A illustrates that computer 102 and printer 104 that have pairedmay be connected by establishing wireless connections 112 and 114,respectively, to the same access point 108 of a network 110. Network 110may be a home network, an enterprise network, the Internet or any othersuitable network. Any suitable technique may be used to form wirelessconnections 112 and 114, including techniques that employ knowninfrastructure type protocols. As one example, wireless connections 112and 114 may be formed using a WI-FI protocol. Though, the specificprotocol used is not critical to embodiments of the invention.

FIG. 1A illustrates schematically a Layer 3 connection 116 formedbetween computer 102 and printer 104 through wireless connections 112and 114 to access point 108. It should be appreciated that connection116 is formed over wireless connections 112 and 114 and is shownseparately for representation purposes only. Connection 116 may be anysuitable Layer 3 connection, such as an IP connection, established overa supporting Layer 2 connection.

Connection 116 is established between computer 102 and printer 104 afterthe devices pair in accordance with a known technique or any techniquedeveloped in the future. The devices may discover each other inaccordance with any suitable device discovery mechanism. For example,computer 102 and printer 104 may discover each other using a devicediscovery mechanism operating at Layer 3, such as in accordance with anIP-based service discovery protocol. Simple Service Discovery Protocol(SSDP), Bonjour, Web Service (WS) Discovery or any other suitableprotocol may be utilized.

Computer 102 may store information about capabilities of printer 104obtained in conjunction with pairing with and establishing connection116 to printer 104 in any suitable manner. The information may also bepresented to user 106 of computer 102 in a suitable way. For example,the information may be presented by adding a representation of printer104 to a list of devices installed on computer 102.

Once computer 102 and printer 104 have paired, if printer 104 is notactively in use, communications to printer 104 at Layer 3 may besuspended. As illustrated in FIG. 1B, this may involve disconnectingprinter 104 from access point 108 by terminating connection 114 whichresults in terminating connection 116 between computer 102 and printer104. Though computer 102 may be connected via access point 108 to otherdevices (not shown), connection 112 established to connect to printer104 via access point 108 may be terminated when connection 114terminates. Alternatively or additionally, connection 116 may bedirectly terminated and/or connection 112 may be terminated.

Once the Layer 3 connection between computer 102 and printer 104 hasbeen terminated, computer 102 may monitor presence of printer 104 usinga Layer 2 device discovery mechanism 118, as shown schematically in FIG.1C. Peer-to-peer protocols, such as a WI-FI DIRECT™, BLUETOOTH® or othersuitable Layer 2 protocol may be utilized.

Any suitable Layer 2 device discovery mechanism may be used. Forexample, computer 102 may monitor for printer 104 by sending requestsfor information about presence of printer 104. If printer 104 ispresent, it may respond to the requests by sending to computer 102appropriate responses indicating presence of printer 104. The requestsand responses may be exchanged between the devices in any suitablemanner. For example, WI-FI Probe Requests in accordance with a WI-FIDIRECT™ protocol may be sent periodically. If printer 104 is present, itmay respond to a WI-FI Probe Request with a WI-FI Probe Response tonotify computer 102 of its presence.

In some embodiments, printer 104 may notify computer 102 and otherdevices of its presence by sending periodic messages in accordance witha Layer 2 device discovery protocol, such as Layer 2 broadcast messages.It should be appreciated that the requests may be sent in a waydifferent from sending requests at evenly spaced intervals. Thus,requests for device presence or notifications of device's presence maybe sent with any suitable timing.

In some embodiments, computer 102 may not monitor presence of printer104 continuously. Rather, Layer 2 device discovery mechanism 118 may beinitiated in response to a suitable trigger event. For example, userinput may be received though computer 102 indicating an attempt to useprinter 104. The user input may comprise, for example, an indication toexecute an application that accesses printer 104. In some embodiments,presence of printer 104 may be determined in response to powering upprinter 104. Prior to a trigger event, no monitoring for printer 104 maybe conducted by computer 102.

It should be appreciated that computer 102 is shown to determinepresence of printer 104 by way of example only as, in some scenarios,both devices may determine each other's presence either continuously orin response to a trigger. A device may probe for presence of a remotedevice based on a type of the probing device. For example, a computermay probe for remote devices but devices that operate as computerperipherals may not actively probe for other devices.

Regardless of a way in which presence of printer 104 may be determined,information about presence of printer 104 may be provided throughcomputer 102 in a suitable manner. For example, when printer 104 isdetermined to be available (e.g., when printer 104 responds to a proberequest), the information may be displayed on a user interface ofcomputer 102 in a list of available devices, that is updated as computer102 determines presence of printer 104. Though, it should be appreciatedthat the information on presence of printer 104 may be provided in anysuitable way.

In some embodiments, when use of printer 104 is desired, connection 116between computer 102 and printer 104 may be reestablished based ondetermining presence of printer 104 using a Layer 2 device discoverymechanism, as shown in FIG. 1D. Connection 116 may be reestablished whenprinter 104 rejoins network 110 by reconnecting to access point 108 viawireless connection 114. Printer 104 may be triggered to rejoin thenetwork in any suitable way, including in response to commands sent overa direct Layer 2 connection.

An indication of use of printer 104 may be received in any suitable way,such as, for example, through a user interface of computer 102. Inembodiments where presence of printer 104 is determined upon receivingan indication of an attempt to use printer 104, connection 116 may bereestablished once computer 102 determines presence of printer 104.Accordingly, in such embodiments, determining presence of printer 104 inaccordance with a Layer 2 device discovery mechanism shown in connectionwith FIG. 1C is followed by reestablishing connection 116 based on thedetermination, as illustrated in FIG. 1D. Once connection 116 isreestablished, printer 104 may be utilized.

In some embodiments, a direct connection, rather than a connectionthrough an access point, may be established between devices that havepaired. The direct wireless connection may be formed in scenarios wheredevices are used in proximity to each other, such as in a home or officeenvironment. It should be appreciated that the wireless peer-to-peerconnection to a remote device may be established in many differentscenarios, as embodiments of the invention are not limited in thisrespect.

FIG. 2 illustrates a scenario in which a wireless peer-to-peerconnection is established via WI-FI DIRECT™ by devices that have paired.FIG. 2 shows computer 202 and printer 204, which may be similar tocomputer 102 and printer 104 shown in FIG. 1. However, in FIG. 2A, aLayer 2 connection established between computer 202 and printer 204after the devices have paired is a direct peer-to-peer connection 206,rather than a connection through access point 108.

In this example, direct connection 206 may be established in accordancewith a WI-FI DIRECT™ protocol. Though, it should be appreciated thatdirect connection 206 may be established between computer 202 andprinter 204 in accordance with any other short-range communicationprotocol, such as a BLUETOOTH® or other protocol. It should also beappreciated that computer 202 and printer 204 may be connected to otherdevices via suitable connections, which is not shown for the sake ofsimplicity.

FIG. 2A illustrates schematically that a Layer 3 over a Layer 2connection, such as an IP connection 208 over a non-IP connection 206,may be formed between computer 202 and printer 204. It should beappreciated that connection 208 is formed over connection 206 and isshown separately for representation purposes only.

Subsequent interactions between computer 202 and printer 204 may proceedin a way similar to that shown with reference to FIG. 1. Hence, when IPconnection 208 to printer 204 is not actively used, printer 204 maysuspend communications at Layer 3 to computer 202. This may involveterminating connection 208 which allows terminating underlyingconnection 206 established in accordance with a WI-FI DIRECT™ protocol.FIG. 2B illustrates that connections 206 and 208 to printer 204 may beterminated. Presence of printer 204 may be detected using a Layer 2device discovery mechanism in accordance with some embodiments,similarly to determining device presence as shown in FIG. 1C.

FIG. 2B illustrates that, when Layer 3 connection 208 and underlyingLayer 2 connection 206 to printer 204 are terminated, printer 204 mayestablish a connection at Layer 3 to another device. In someembodiments, a device may be capable of supporting only a singlepoint-to-point connection at Layer 2 with another device. For example,printer 204 may be able to maintain only a single connection at Layer 2to another device. Because the techniques described herein allowdetermining presence of printer 204 using a Layer 2 device discoverymechanism instead of a conventional IP-based mechanism, the IPconnection and the underlying Layer 2 connection to printer 204 may beterminated when the printer is not in use.

Accordingly, as shown in FIG. 2B, when printer 204 disconnects fromcomputer 202, printer 204 may establish a Layer 2 connection 210 toanother device, such as, for example, a computer 214. Layer 2 connection210 may be, for example, a WI-FI DIRECT™ connection that supports aLayer 3 connection 212. Connection 212 may be used to accessfunctionality of printer 204 through computer 214. Thus, determiningdevice presence using a Layer 2 device discovery mechanism in accordancewith some embodiments may increase device availability, which isillustrated above using an example of printer 204, which is available tocomputer 214 because the printer's connection capacity is not consumedby a connection to computer 202.

It should be appreciated that, after connections 206 and 208 to printer204 terminate and a Layer 2 device discovery mechanism is used todetermine presence of printer 204, if use of printer 204 is desired, theLayer 2 and Layer 3 connections to printer 204 may be reestablishedbased on monitoring presence of printer 204, which is not shown in moredetail for the sake of simplicity.

FIG. 3 is a block diagram of an illustrative embodiment of componentswithin a computing device 300 adapted to perform device presencemonitoring at Layer 2 to support a Layer 3 connection, in accordancewith some embodiments. The components shown in FIG. 3 may be implementedwithin any suitable device. For example, computer 102 (FIG. 1) orcomputer 202 (FIG. 2) may implement the components. Though, it should beappreciated that any suitable device may store the components shown inFIG. 3 in a suitable memory location and to execute the components viaone or more processors.

FIG. 3 illustrates that computing device 300 may comprise a userinterface component 302, which may be used to present a list of devicescurrently available to the user. The currently available devices may bedetermined by monitoring presence of devices with which computer 300 haspaired using a conventional technique, such as an IP-based servicediscovery protocol or using a Layer 2 device discovery mechanism inaccordance with some embodiments.

Suitable user input may be received in connection with user interface302 indicating a selection of a device from the list of availabledevices. An exemplary implementation of user interface component 302 isshown in more detail in FIG. 4A.

FIG. 3 illustrates that computing device 300 may comprise a device store304 that may store a collection of device objects 306 each representinga device to which computing device 300 has paired. Each device objectmay comprise suitable information on properties of a correspondingdevice. For example, if computing device 300 comprises computer 102shown with reference to FIG. 1, a device object 307 from device objects306 may store information on printer 104 after printer 104 paired withcomputer 102.

Properties of the device stored in the device object may comprise deviceidentification information, such as its Friendly name, ManufacturerName, Model Name/Number and other suitable properties of the device. Theproperties of the device may also indicate whether the device iscurrently available. Thus, user interface component 302 may query devicestore 304 for the list of available devices. A device object may alsocomprise information on how to connect to the device (e.g., an HTTP URL)and any other suitable information on the device.

FIG. 3 illustrates that computing device 300 may comprise an IP-baseddiscovery module 308. IP-based discovery module 308 may operate tomonitor device discovery in accordance with an IP-based servicediscovery protocol, such as, for example, SSDP, Bonjour, Web Service(WS) Discovery or any other protocol. IP-based discovery module 308 maytherefore be used to collect device presence information and propertiesof the device over an IP network. To monitor device presence usingIP-based discovery module 308, an IP connection to the monitored devicemay be maintained throughout the monitoring.

The presence information collected by IP-based discovery module 308 maybe stored in a corresponding device object from device objects 306 indevice store 304. This information may be updated when IP-baseddiscovery module 308 detects changes in availability of the device.

When an indication of use of a device is received in a suitable manner(e.g., by selecting the device via user interface component 302), adevice protocol module 310 may access device store 304 to obtaininformation stored in a corresponding device object. The information maycomprise properties of the device and information on how to connect toand interact with the device using a device class specific protocol overIP. As an example, when a computer interacts with an UPnP Digital MediaServer device to retrieve steaming data from the server, a deviceprotocol module 310 may retrieve the HTTP URL from a correspondingdevice object and send UPnP messages (e.g., in accordance with the UPnPstandard) as HTTP requests to that URL.

When presence of a remote device is monitored using IP-based discoveryprotocols, a Layer 3 connection to the device may be maintained. Adevice monitoring at Layer 3 may send messages in accordance with aprotocol used (e.g., IP multicast messages) announcing its presence. Thedevice may also respond to requests sent by other devices (e.g., IPmulticast messages) monitoring its presence.

In some embodiments, device presence using an IP-based service discoverymay be supplemented by device discovery at Layer 2. Accordingly,referring back to FIG. 3, computing device 300 may include Layer 2discovery module 312 that executes to determine device presence inaccordance with a suitable Layer 2 device discovery mechanism. Forexample, a WI-FI DIRECT™ or BLUETOOTH® protocol may be used to determinedevice presence, by either continuously monitoring device presence ordetermining device presence is response to a suitable trigger event.

Determining presence of a remote device using a Layer 2 device discoverymechanism does not depend on an IP connection with the remote device.Thus, obtaining device presence information through device discovery atLayer 2 allows reducing power consumption without degrading the device'savailability due to the elimination of the requirement to keep the Layer3 connection to the device alive and to therefore maintain an underlyingLayer 2 connection. Device presence may be determined at Layer 2 whilethe Layer 3 connection to the device is terminated such that the Layer 3connection may be reestablished when an indication of use of the remotedevice is received.

In some embodiments, computing device 300 may utilize only a Layer 2device discovery mechanism implemented by Layer 2 discovery module 312to monitor presence of a remote device when the remote device is not inuse. In other embodiments, IP-based discovery module 308 may operate todetermine device presence while an IP connection to the device remainsactive. When the IP connection is terminated, Layer 2 discovery module312 may be initiated to conduct device discovery using a Layer 2 devicediscovery mechanism.

As discussed above, because determining device presence in accordancewith a Layer 2 device discovery mechanism does not require a Layer 3connection (e.g., an IP connection) to the device, an underlying Layer 2connection supporting the Layer 3 connection may be terminated as well.For example, when a remote device (e.g., printer 104) disconnects froman access point (e.g., access point 108), a Layer 2 connection to theaccess point may be terminated (FIGS. 1A and 1B). As another example, adirect Layer 2 connection to a remote device, such as printer 204, maybe terminated (FIGS. 2A and 2B).

Computing device 300 may include a Layer 2 connection manager module 314that may be utilized to reestablish a Layer 2 connection to the remotedevice after the Layer 2 and Layer 3 connections to the device have beenterminated. The Layer 2 connection to the device may be reestablished inresponse to an attempt to use the device or other suitable trigger.

When the device reconnects at Layer 2, IP connectivity over the Layer 2connection to the device may be reestablished. Reestablishing the Layer3 connection may involve requesting or providing an IP address through aDynamic Host Configuration Protocol (DHCP), bringing up the TCP/IP stackor any other suitable way of reconnecting the device at Layer 3.

Once the IP connection to the remote device is reestablished, deviceprotocol module 310 may use previously stored information about theremote device (e.g., information obtained during pairing with thedevice) and the IP connection information to interact with the deviceover the IP connection.

In some scenarios, when the Layer 3 connection to the remote device isreestablished, an IP address of either of the devices may be differentfrom an IP address that the device had during the pairing process. TheIP address may change for a number of reasons. For example, a previouslystored (e.g., in a device object of device store 304) HTTP URL to accessa remote device may become stale. Accordingly, the remote device may bere-discovered at Layer 3 to obtain the current IP address of the device.It should be appreciated that the remote device may re-discovercomputing device 300 as well.

When the use of the device is complete, device protocol module 310 mayinstruct Layer 2 connection manager module 314 to disconnect the Layer 2connection with the device and presence of the device may again bemonitored using a Layer 2 device discovery mechanism in accordance withsome embodiments.

Computing device 300 may comprise other components not shown herein forthe sake of simplicity. Thus, computing device 300 includes one or moreprocessors that may execute the components shown in FIG. 3. It should beappreciated that computing device 300 may comprise any suitablecomponents, as embodiments of the invention are not limited in thisrespect.

FIG. 4A illustrates an exemplary user interface, such as a devicemanager interface 400, provided by user interface component 302 throughwhich a user may view and select devices paired with computing device300. As shown in FIG. 4A, device manager interface 400 may comprise alist of installed devices 402 and a list of currently available devices404.

List of installed devices 402 may include representations of devicespaired with computing device 300. Computing device 300 may storeinformation on capabilities of each of such devices in a suitablestorage medium, such as device store 304 (FIG. 3). Drivers forcontrolling the devices may be installed on computing device 300 orcomputing device may otherwise be configured to access services providedby those devices.

FIG. 4A illustrates by way of example that list of installed devices 402may comprise a monitor 406, a TV 408, a printer 410 (“printer A”), aprinter 412 (“printer B”), a keyboard 414 and a mouse 416. It should beappreciated that icons visually resembling corresponding devices aredisplayed in list of installed devices 402 in FIG. 4A by way of exampleonly, and any suitable indication of installed device(s) may beutilized, as embodiments of the invention are not limited in thisrespect.

Not all of the devices paired with computing device 300 may be availablefor use at a certain point in time. For example, a remote device, suchas a wireless printer with which computing device has paired, may beturned off and thus become unavailable for printing documents. Asanother example of a scenario when a remote device becomes unavailablefor use through computing device 300 may include carrying the remotedevice away so that it is no longer within the reach of an access pointor a wireless radio. Accordingly, presence of these devices may bemonitored by computing device 300 so that functionality of any of thedevices may be accessed without a delay when use of the device isdesired.

A remote device may be taken to be available when a suitable mechanismused to determine the device's presence indicates that the device iscurrently available—e.g., that one or more responses to probe requestsare received from the device, an appropriate notification is receivedfrom the device or the device is otherwise determined to be present. Asshown in FIG. 4A, device manager interface 400 may comprise list ofavailable devices 404 which indicates, based on device presencemonitoring, which of the installed devices 406, 408, 410, 412, 414 and416 are currently available.

In some embodiments, device presence may be continuously monitored usinga Layer 2 device discovery mechanism. If a remote device is determinedto be present, this may be indicated in a suitable manner, such as bydisplaying a representation of the device in list of available devices404. As shown in FIG. 4A, list of available devices 404 comprisesmonitor 406, printer 410, keyboard 414 and mouse 416 indicating thatthese devices may be used through computing device 300.

One or more of the currently available devices indicated on list ofavailable devices 404 may be selected using any suitable mechanism. Forexample, user input may be received in connection with a representationof a device that is desired to be used. FIG. 4A illustrates that, as anexample, printer 410 which is the only printer available for use amonginstalled printers 410 and 412, may be selected, as schematically shownby an arrow 418. When presence of printer 410 is determined inaccordance with a Layer 2 device discovery mechanism while a Layer 3connection to the printer is terminated, upon the selection of printer410 for use, a Layer 3 connection to printer 410 may be reestablished.

For comparison purposes, FIG. 4B illustrates another device managerinterface 420 which includes only a list of installed devices 422. Listof installed devices 422 comprises, by way of example only, the samedevices as those shown in list of installed devices 402 in FIG. 4A. Sucha user interface may be used in place of device manager interface 400 inembodiments in which a computer does not monitor for presence of remotedevices once a Layer 3 connection is terminated. In such scenarios, thecomputer may not generate a list of available devices.

FIG. 5 illustrates schematically an environment 500 in which anexemplary device A (501) may monitor presence of a remote exemplarydevice B (502) using a Layer 2 device discovery mechanism in accordancewith some embodiments after the devices pair. FIG. 5 also illustrateslayers of the OSI layered model of network connectivity that mayparticipate in monitoring device presence as illustrated in thisexample.

Accordingly, device A may include, starting from the lowest layer, aLayer 2 module 504A, a TCP/IP module 506A, an IP-based discovery module508A, and an application module 510A. In this OSI model, each layerrelies on communication being established at the lower layers, as knownin the art. Similarly, device B may include, starting from the lowestlayer, a Layer 2 module 504B, a TCP/IP module 506B, an IP-baseddiscovery module 508B, and an application module 510B. It should beappreciated that devices A and B may include any other suitablecomponents used to monitor device presence in accordance with someembodiments and to perform other functionality.

As shown schematically in FIG. 5, devices A and B pair at 512. Thepairing may involve devices' discovering each other via a Layer 2protocol, which uses Layer 2 module 504A at device A and Layer 2 module504B at device B, and establishing a Layer 3 (e.g., an IP) connectionbetween the devices via TCP/IP modules 506A and 506B. The Layer 3connection may be utilized by an IP-based discovery protocol of IP-baseddiscovery modules 508A and 508B that allow devices A and B to learnabout each other's capabilities and services. These capabilities andservices may be utilized by application modules 510A and 510B to executea suitable application that provides services when devices A and Binteract.

After the pairing and establishing of the Layer 3 connection betweendevices A and B is complete, device B may disconnect at Layer 3, whichavoids the need to maintain the underlying Layer 2 connection to deviceB which is therefore terminated at 514. Device B may disconnect atLayers 2 and 3 when it is determined that the Layer 3 connection to thatdevice is not actively used or based upon other suitable determination.Disconnecting Device B terminates, as discussed above, the Layer 3 andLayer 2 connections between devices A and B.

Once the Layer 3 and Layer 2 connections to device B are terminated,device A may monitor presence of device B at Layer 2 (516), such asusing a suitable Layer 2 device discovery mechanism. As presence of aremote device is monitored using a Layer 2 device discovery mechanism,updates about the device's presence may be provided to the applicationon the monitoring device that may use functionality of the remotedevice. Thus, FIG. 5 shows that Layer 2 module 504A may provide updates(518) on availability of device B to application module 510A, based onmonitoring presence of device B using a suitable Layer 2 devicediscovery mechanism. The updates may be used to, for example, update alist of devices currently available to a user of device A (e.g., list ofavailable device 404 in FIG. 4A).

When use of device B is desired, Layer 2 connection to device B may bereestablished (520), based on monitoring presence of device B using asuitable Layer 2 device discovery mechanism. Reconnecting device B atLayer 2 allows reestablishing a Layer 3 connection to the device.Accordingly, devices A and B may interact so that device B may be used(522) to provide services to a user. The services may be provided overthe reestablished Layer 3 connection.

FIG. 6 is illustrates another environment 600 in which remote devicepresence is determined in response to an indication of an attempt to usethat device. FIG. 6 includes features similar to those illustrated inFIG. 5. Thus, FIG. 6 includes device A (601) and device B (602) eachcomprising the same layers in accordance with the OSI model as thosefound in devices 501 and 502. It should be appreciated that devices Aand B may include any other suitable components used to monitor devicepresence in accordance with some embodiments and to perform otherfunctionality.

In FIG. 6, devices A and B may pair at 612 and disconnect at Layer 2(614) and at Layer 3, in a way similar to that shown in conjunction withFIG. 5. However, no continuous monitoring of presence of device B bydevice A may be conducted in the example of FIG. 6 while device B isdisconnected. Rather, determining presence of device B may be performedupon a suitable trigger event, such as an indication of an attempt touse device B at 616.

Accordingly, in response to the indication, presence of device B may bedetermined (618) at Layer 2—for example, using a suitable Layer 2 devicediscovery mechanism. If presence of device B is determined at Layer 2,the Layer 2 connection to device B may be reestablished at 620.Reconnecting device B at Layer 2 allows reestablishing a Layer 3connection to the device. Next, devices A and B may interact so thatdevice B may be used (622) to provide services to a user. The servicesmay be provided over the reestablished Layer 3 connection.

FIG. 7 illustrates a process 700 of monitoring device presence at Layer2 in accordance with some embodiments. Process 700 illustrates anexample of operating devices indicated by way of example as “device A”and “device B.” Thus, process 700 includes two processes executed byeach of devices A and B.

In this instance, device A may be, for example, a computer (e.g.,computer 102 or 202), whereas device B may be a remote device, such as aprinter (e.g., printer 104 or 204) or other remote device engaging intoa wireless connection with the computer. Though, it should beappreciated that any suitable types of devices having short-rangecommunication capability may be substituted, as embodiments of theinvention are not limited in this respect. The wireless connectionbetween devices A and B may be established via an access point or it maybe a wireless peer-to-peer connection.

Further, it should be appreciated that process 700 is described for anembodiment in which device A monitors presence of device B when device Bis not actively used by way of example only. In some scenarios, bothdevices A and B may monitor each other's presence at Layer 2 inaccordance with the techniques described herein. It should also beappreciated that devices A and B may engage in communications with otherdevices and may monitor these other devices' presence as well.

Process 700 may start at any suitable time. In some scenarios, process700 may start when devices A and B appear in the vicinity of an accesspoint to a network. For example, the devices may be in the environmentas shown in connection with FIG. 1A. In some embodiments, process 700may begin when devices A and B are within the reach of each other andmay establish a direct wireless connection, such as in the example shownin FIG. 2A.

Regardless of a way in which process 700 initiates, devices A and B mayfirst connect at Layer 2. The Layer 2 connection between the devices maybe a WI-FI connection via an access point, or a direct connection inaccordance with a WI-FI DIRECT™, BLUETOOTH® or other suitableshort-range communication protocol. Devices A and B may then establish aLayer 3 connection over the underlying Layer 2 connection, and discovereach other's capabilities at Layer 3.

Accordingly, device A may discover device B at Layer 3, as shown atblock 702. Similarly, as shown at block 704, device B may discoverdevice A at Layer 3. The Layer 3 connection may be an IP connection,though embodiments of the invention are not limited in this respect. Thedevice discovery at Layer 3 may be performed using a suitable IP-baseddiscovery protocol.

Next, information obtained in conjunction with establishing the Layer 3connection between devices A and B may be stored. Thus, device A maystore, at block 706, information about capabilities of device B. DeviceB, in turn, may store information about Device A, at block 708. Storingthis information may avoid the need to conduct the device discoveryagain, when use of device B is desired.

When it is determined that device B is not in use and the Layer 3connection to device B is therefore not actively used (though the Layer3 connection may be in use to monitor presence of device B), device Bmay suspend communications at Layer 3. Suspending the Layer 3communications may involve disconnecting device B at Layer 3, which isshown at block 710 where device A disconnects at Layer 3 from device Band at block 712 where device B disconnects at Layer 3 from device A. Itshould be appreciated that disconnecting device B at Layer 3 may involveterminating a Layer 3 connection via an access point or terminating adirect Layer 3 connection to device B (e.g., a WI-FI DIRECT™connection).

In some embodiments, when the Layer 3 connection to device B isestablished at block 702, a timer may be initiated to track a lifetimeof the Layer 3 connection. After the Layer 3 connection has beenmaintained for a period of time that has exceeded a certain time limitand if the connection is not actively used, the Layer 3 connection maybe terminated, at block 712 and, consequently, at block 710.

Disconnecting device B at Layer 3 makes it unnecessary to maintain theLayer 2 connection to that device. Accordingly, devices A and B candisconnect from each other at Layer 2, as shown at blocks 714 and 716.It should be appreciated that operations at blocks 714 and 716 are shownto follow operations at blocks 710 and 712 by way of example only as theLayer 2 connection to device B may be terminated prior to terminatingthe Layer 3 connection to device B. Furthermore, in some scenarios, theLayer 3 and Layer 2 connections to device B may be terminated at thesame time.

While device B suspends its communications at Layer 3 and the Layer 3and Layer 2 connections between devices A and B are thereforeterminated, presence of device B may be monitored by device A at block718. Device A may monitor presence of device B using a suitable Layer 2device discovery mechanism. In the example illustrated, device B, ifavailable, may respond to probe requests of device A, at block 720.Though, device presence monitoring in accordance with a Layer 2 devicediscovery mechanism may be performed in any other suitable manner. Insome embodiments, the monitoring may be performed upon a suitabletrigger which may be provided at block 719.

In some embodiments, an indication of presence of device B that dependson the monitoring at blocks 718 and 720 may be provided in a suitablemanner through device A. For example, a representation of availabilityof device B may be provided on a user interface of Device A. Forexample, such representation may be displayed on list of availabledevices 402 of device manager interface 400 (FIG. 4A). Though, it shouldbe appreciated that the indication of presence of device B may beprovided in any suitable manner, as embodiments of the invention are notlimited in this respect.

Next, an indication of an attempt to use device B may be received atDevice A, at block 724. The indication may be received by selectingdevice B for use via a user interface, such as, for example, list ofavailable devices 402 (FIG. 4A). As another example, an indication of anattempt to use functionality of device B may be received. It should beappreciated that the indication of an attempt to use device B may bereceived in any suitable manner, as embodiments of the invention are notlimited in this respect.

In response to receiving the indication of an attempt to use device B atblock 724, the Layer 3 connection to device B may be reestablished atblocks 726 and 728, based on the monitoring of presence of device B atLayer 2. The Layer 3 connection to device B may be reestablished over anunderlying Layer 2 connection that is also reestablished to support theLayer 3 connection.

After device B reconnects to device A at Layer 3, devices A and B mayinteract so that device B may be used, as shown at blocks 730 and 732.For example, if devices A and B comprise a computer and a wirelessremote printer, a user of the computer may instruct the printer to printa document. Process 700 may then end. It should be appreciated, however,that process 700 may be continuous. Accordingly, after the requested useof device B is completed (e.g., a document is printed if device Bcomprises a remote printer), process 700 may return to blocks 710 and712 where device B may again disconnect at Layer 3. While the Layer 3connection to device B is terminated, presence of device B maysubsequently be again monitored as shown in FIG. 7.

In some embodiments, rather than continuously monitoring device presenceat Layer 2, presence of a paired with remote device may be determined inresponse to a trigger event, such as an indication that use of theremote device is desired. An example of such a process 800 isillustrated with reference to FIG. 8 where an exemplary device A pairswith an exemplary device B that subsequently disconnects from device Aat Layer 3. While device B is disconnected from device A at Layer 3, inresponse to an indication of an attempt to use device B, device A maydetermine presence of device B.

Process 800 may be performed in various environments where it may bemore practical to determine presence of a remote device in response to atrigger event, rather than to continuously monitor presence of theremote device. For example, determining device presence in response to atrigger may be used in settings where a device, such as a computer, mayinteract with one or more media devices to transfer streaming data fromthe computer to the media devices. As another example, the computer mayaccess file sharing services provided by the remote device. Though, itshould be appreciated that any suitable type of interaction with theremote device may be performed in response to a trigger, as embodimentsof the invention are not limited in this respect.

Furthermore, determining device presence in response to a trigger may bepractical in settings where users of different devices desire to use anapplication (e.g., a computer game) that may be concurrently executed onboth devices and may be accessed by each user via the user's device. Ifan indication of using the shared application is received from a user ofone of such devices, this device may initiate determination of presenceof another device, using a Layer 2 device discovery mechanism inaccordance with some embodiments. Also, both of the devices executingthe application may determine each other's presence.

Referring back to FIG. 8, processing at blocks 802-816 may be performedsimilar to processing at blocks 702-716 described in conjunction withFIG. 7. The processing at blocks 802-816 is therefore not describedherein for the sake of brevity. However, in the example illustrated,presence of device B is not monitored continuously. Accordingly, atblock 818, an indication of an attempt to use device B may be receivedin a suitable manner. For example, device B may be selected from a listof installed devices (e.g., list of installed devices 402 in FIG. 4A).Alternatively or additionally, suitable user input may be received bydevice A indicating an attempt to execute an application that accessesdevice B. As another example, the indication may comprise powering updevice B or other action indicating an attempt to use device B. Though,embodiments of the invention are not limited to a particular way inwhich an indication of an attempt to use device B may be received atdevice A, and this indication may be received in any suitable manner.

Regardless of a way in which the indication of an attempt to use deviceB is received at block 818, in response to the indication, device A maydetermine presence of device B. The determination may be done using aLayer 2 device discovery mechanism, in accordance with some embodimentsof the invention. For example, device A may send a request to device B,in which case device B, if present, may respond to the request, as shownat block 822, by sending to device A a suitable response notifyingdevice A of its presence. It should be appreciated that any suitabletype of mechanism at Layer 2 may be used by device A to determinepresence of device B in response to an indication of use of device B, asembodiments of the invention are not limited in this respect.

Next, process 800 may branch at decision block 824 depending on whetherit is determined that device B is present. If it is determined thatdevice B is present, process 800 may proceed to block 826 where anindication that depends on presence of device B may be provided throughdevice A. The indication may comprise adding a representation of deviceB to a list of devices currently available for use to a user of deviceA. Though, any other suitable indication of presence of device B may beprovided by device A, which is not limited to visually displaying arepresentation of device B on a user interface of device A.

Alternatively, if presence of device B is not determined in response toan attempt of its use, a suitable alternative action may be performed,at block 836. The alternative action may comprise suggesting to theuser, in a suitable way, another device to use instead of device B.Alternatively or additionally, one or more notifications may be providedto the user informing the user that device B is not available and whatother devices, if any, are available to be used instead of device B inthe same or similar manner. It should be appreciated that any suitabletype of an alternative action may be taken, as embodiments of theinvention are not limited in this respect.

After presence of device B is determined, the Layer 3 connection todevice B may be reestablished at blocks 828 and 830, based on thedetermining of presence of device B at Layer 2. The Layer 3 connectionto device B may be reestablished over an underlying Layer 2 connectionthat is also reestablished to support the Layer 3 connection.Reconnecting device B at Layer 2 may involve, in embodiments wheredevices A and B are connected through the same access point,reconnecting device B to the access point (e.g., using a WI-FIprotocol). In embodiments where devices A and B are directly connectedto each other, a WI-FI DIRECT™ or BLUETOOTH® connection to device B maybe formed.

After device B reconnects to device A at Layer 3, device B may be usedin accordance with its functionality, as shown at blocks 832 and 834.Process 800 may then end. Though, it should be appreciated that, afterdevice B has been used in a requested manner, process 800 may return toblocks 810 and 812 where devices A and B can disconnect from each otherat Layer 3 and remain disconnected until an indication of use of deviceB is received. Accordingly, any time that device B is not actively usedby device A, no active Layer 3 connection, such as an IP connection, maybe maintained between the devices.

In some embodiments, the Layer 3 connection to device B may bereestablished for a certain period of time that may be specified inassociation with an event triggering the reestablishment of theconnection. In such embodiments, process 800 may return to blocks 810and 812 once the Layer 3 connection terminates upon the expiration ofthe period of time.

Regardless of whether device presence is determined at Layer 2 asdescribed in connection with FIG. 7 or FIG. 8, eliminating the need tokeep the IP connection to device B alive while device B is not activelyused may reduce power consumption by both devices A and B. Moreover, anoverhead that would otherwise be associated with sending messages tomaintain a Layer 3 connection may be avoided. This may lead to a morecost-efficient use of the devices because the devices may be operatedusing battery as a power source for an extended period of time.

FIG. 9 illustrates an exemplary environment in which device presence maybe monitored in accordance with some embodiments. The environmentcomprises a computer 902 shown by way of example as a laptop computerthat may connect to a remote device, such as a TV 904, to stream data(e.g., audio and/or video data) to TV 904. A user 905 may controlcomputer 902 using any suitable mechanism.

As shown in FIG. 9A, laptop 902 and TV 904 may pair and connect via adirect Layer 2 connection 906, such as a WI-FI DIRECT™ connection.Connection 906 may be not dependent on an access point 908 of a network910. A Layer 3 connection 912 which may be, for example, an IPconnection, may be established to TV 904 over Layer 2 connection 906 tolearn about functionality provided by the device.

FIG. 9B illustrates that, if Layer 3 connection 912 to TV 904 is notactively used to access services provided by TV 904, connection 912 maybe terminated. Terminating Layer 3 connection 912 may involveterminating supporting Layer 2 connection 906 which avoids expendingpower that would otherwise be required to maintain the infrastructure ofthe Layer 2 connection. Power may be further saved because an overheadthat would otherwise be required to maintain the Layer 3 connection maybe avoided.

While Layer 3 connection 912 to TV 904 is terminated, presence of TV 904may be monitored using a Layer 2 device discovery mechanism 914, inaccordance with some embodiments. Accordingly, computer 902 and TV 904may interact so that computer 902 is notified of presence of TV 904which indicates availability of TV 904.

When an indication of use of TV 904 is received (e.g., user inputreceived through computer 902), Layer 2 connection 906 to TV 904 may bereestablished and, as a result, Layer 3 connection 912 to TV 904 may bereestablished as well, as shown in FIG. 9D. Once connection 912 to TV904 is reestablished, laptop 902 and TV 904 may interact. In thisexample, laptop 902 may stream data to TV 904, as schematically shown byan arrow 916 in FIG. 9E. Though, it should be appreciated thatembodiments of the invention are not limited to a purpose and manner inwhich devices that may detect device presence using a Layer 2 devicediscovery mechanism interact.

FIG. 10 illustrates an example of a suitable computing systemenvironment 1000 on which some embodiments of the invention may beimplemented. It should be appreciated that the computing systemenvironment 1000 is only one example of a suitable computing environmentand is not intended to suggest any limitation as to the scope of use orfunctionality of the invention. Neither should the computing environment1000 be interpreted as having any dependency or requirement relating toany one or combination of components illustrated in the exemplaryoperating environment 1000.

Some embodiments of the invention are operational with numerous othergeneral purpose or special purpose computing system environments orconfigurations. Examples of well-known computing systems, environments,and/or configurations that may be suitable for use with embodiments ofthe invention include, but are not limited to, personal computers,server computers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of the above systemsor devices, and the like.

The computing environment may execute computer-executable instructions,such as program modules. Generally, program modules include routines,programs, objects, components, data structures, etc. that performparticular tasks or implement particular abstract data types. Someembodiments of the invention may also be practiced in distributedcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed computing environment, program modules may be located inboth local and remote computer storage media including memory storagedevices.

With reference to FIG. 10, an exemplary system for implementing someembodiments of the invention includes a general purpose computing devicein the form of a computer 1010. Components of computer 1010 may include,but are not limited to, a processing unit 1020, a system memory 1030,and a system bus 1021 that couples various system components includingthe system memory to the processing unit 1020. The system bus 1021 maybe any of several types of bus structures including a memory bus ormemory controller, a peripheral bus, and a local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus also known as Mezzanine bus.

Computer 1010 typically includes a variety of computer readable media.Computer readable media can be any available media that can be accessedby computer 1010 and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer readable media may comprise computer storage mediaand communication media. Computer storage media includes both volatileand nonvolatile, removable and non-removable media implemented in anymethod or technology for storage of information such as computerreadable instructions, data structures, program modules or other data.Computer storage media includes, but is not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can accessed by computer 1010. Communication media typicallyembodies computer readable instructions, data structures, programmodules or other data in a modulated data signal such as a carrier waveor other transport mechanism and includes any information deliverymedia. The term “modulated data signal” means a signal that has one ormore of its characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of the any of the aboveshould also be included within the scope of computer readable media.

The system memory 1030 includes computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) 1031and random access memory (RAM) 1032. A basic input/output system 1033(BIOS), containing the basic routines that help to transfer informationbetween elements within computer 1010, such as during start-up, istypically stored in ROM 1031. RAM 1032 typically contains data and/orprogram modules that are immediately accessible to and/or presentlybeing operated on by processing unit 1020. By way of example, and notlimitation, FIG. 10 illustrates operating system 1034, applicationprograms 1035, other program modules 1036, and program data 1037.

The computer 1010 may also include other removable/non-removable,volatile/nonvolatile computer storage media. By way of example only,FIG. 10 illustrates a hard disk drive 1040 that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive 1051that reads from or writes to a removable, nonvolatile magnetic disk1052, and an optical disk drive 1055 that reads from or writes to aremovable, nonvolatile optical disk 1056 such as a CD ROM or otheroptical media. Other removable/non-removable, volatile/nonvolatilecomputer storage media that can be used in the exemplary operatingenvironment include, but are not limited to, magnetic tape cassettes,flash memory cards, digital versatile disks, digital video tape, solidstate RAM, solid state ROM, and the like. The hard disk drive 1041 istypically connected to the system bus 1021 through a non-removablememory interface such as interface 1040, and magnetic disk drive 1051and optical disk drive 1055 are typically connected to the system bus1021 by a removable memory interface, such as interface 1050.

The drives and their associated computer storage media discussed aboveand illustrated in FIG. 10, provide storage of computer readableinstructions, data structures, program modules and other data for thecomputer 1010. In FIG. 10, for example, hard disk drive 1041 isillustrated as storing operating system 1044, application programs 1045,other program modules 1046, and program data 1047. Note that thesecomponents can either be the same as or different from operating system1034, application programs 1035, other program modules 1036, and programdata 1037. Operating system 1044, application programs 1045, otherprogram modules 1046, and program data 1047 are given different numbershere to illustrate that, at a minimum, they are different copies. A usermay enter commands and information into the computer 1010 through inputdevices such as a keyboard 1062 and pointing device 1061, commonlyreferred to as a mouse, trackball or touch pad. Other input devices (notshown) may include a microphone, joystick, game pad, satellite dish,scanner, or the like. These and other input devices are often connectedto the processing unit 1020 through a user input interface 1060 that iscoupled to the system bus, but may be connected by other interface andbus structures, such as a parallel port, game port or a universal serialbus (USB). A monitor 1091 or other type of display device is alsoconnected to the system bus 1021 via an interface, such as a videointerface 1090. In addition to the monitor, computers may also includeother peripheral output devices such as speakers 1097 and printer 1096,which may be connected through an output peripheral interface 1095.

The computer 1010 may operate in a networked environment using logicalconnections to one or more remote computers, such as a remote computer1080. The remote computer 1080 may be a personal computer, a server, arouter, a network PC, a peer device or other common network node, andtypically includes many or all of the elements described above relativeto the computer 1010, although only a memory storage device 1081 hasbeen illustrated in FIG. 10. The logical connections depicted in FIG. 10include a local area network (LAN) 1071 and a wide area network (WAN)1073, but may also include other networks. Such networking environmentsare commonplace in offices, enterprise-wide computer networks, intranetsand the Internet.

When used in a LAN networking environment, the computer 1010 isconnected to the LAN 1071 through a network interface or adapter 1070.When used in a WAN networking environment, the computer 1010 typicallyincludes a modem 1072 or other means for establishing communicationsover the WAN 1073, such as the Internet. The modem 1072, which may beinternal or external, may be connected to the system bus 1021 via theuser input interface 1060, or other appropriate mechanism. In anetworked environment, program modules depicted relative to the computer1010, or portions thereof, may be stored in the remote memory storagedevice. By way of example, and not limitation, FIG. 10 illustratesremote application programs 1085 as residing on memory device 1081. Itwill be appreciated that the network connections shown are exemplary andother means of establishing a communications link between the computersmay be used.

Having thus described several aspects of at least one embodiment of thisinvention, it is to be appreciated that various alterations,modifications, and improvements will readily occur to those skilled inthe art.

In exemplary embodiments described above, a connection for establishinga service using a Layer 3 was reestablished based on determining thepresence of a device using a discovery mechanism incorporated as part ofa Layer 2 protocol. Though, in other embodiments, a computing device maysupport different Layer 3 protocols. A connection formed using one Layer3 protocol may be suspended and reestablished based on device discoveryinformation generated with a second Layer 3 protocol. Such an embodimentmay be useful, for example, in scenarios in which different Layer 3protocols have different discovery mechanisms that impact battery drainor performance of a computing device differently.

Such alterations, modifications, and improvements are intended to bepart of this disclosure, and are intended to be within the spirit andscope of the invention. Accordingly, the foregoing description anddrawings are by way of example only.

The above-described embodiments of the present invention can beimplemented in any of numerous ways. For example, the embodiments may beimplemented using hardware, software or a combination thereof. Whenimplemented in software, the software code can be executed on anysuitable processor or collection of processors, whether provided in asingle computer or distributed among multiple computers. Such processorsmay be implemented as integrated circuits, with one or more processorsin an integrated circuit component. Though, a processor may beimplemented using circuitry in any suitable format.

Further, it should be appreciated that a computer may be embodied in anyof a number of forms, such as a rack-mounted computer, a desktopcomputer, a laptop computer, or a tablet computer. Additionally, acomputer may be embedded in a device not generally regarded as acomputer but with suitable processing capabilities, including a PersonalDigital Assistant (PDA), a smart phone or any other suitable portable orfixed electronic device.

Also, a computer may have one or more input and output devices. Thesedevices can be used, among other things, to present a user interface.Examples of output devices that can be used to provide a user interfaceinclude printers or display screens for visual presentation of outputand speakers or other sound generating devices for audible presentationof output. Examples of input devices that can be used for a userinterface include keyboards, and pointing devices, such as mice, touchpads, and digitizing tablets. As another example, a computer may receiveinput information through speech recognition or in other audible format.

Such computers may be interconnected by one or more networks in anysuitable form, including as a local area network or a wide area network,such as an enterprise network or the Internet. Such networks may bebased on any suitable technology and may operate according to anysuitable protocol and may include wireless networks, wired networks orfiber optic networks.

Also, the various methods or processes outlined herein may be coded assoftware that is executable on one or more processors that employ anyone of a variety of operating systems or platforms. Additionally, suchsoftware may be written using any of a number of suitable programminglanguages and/or programming or scripting tools, and also may becompiled as executable machine language code or intermediate code thatis executed on a framework or virtual machine.

In this respect, the invention may be embodied as a computer readablestorage medium (or multiple computer readable media) (e.g., a computermemory, one or more floppy discs, compact discs (CD), optical discs,digital video disks (DVD), magnetic tapes, flash memories, circuitconfigurations in Field Programmable Gate Arrays or other semiconductordevices, or other non-transitory, tangible computer storage medium)encoded with one or more programs that, when executed on one or morecomputers or other processors, perform methods that implement thevarious embodiments of the invention discussed above. The computerreadable storage medium or media can be transportable, such that theprogram or programs stored thereon can be loaded onto one or moredifferent computers or other processors to implement various aspects ofthe present invention as discussed above. As used herein, the term“non-transitory computer-readable storage medium” encompasses only acomputer-readable medium that can be considered to be a manufacture(i.e., article of manufacture) or a machine. Alternatively oradditionally, the invention may be embodied as a computer readablemedium other than a computer-readable storage medium, such as apropagating signal.

The terms “program” or “software” are used herein in a generic sense torefer to any type of computer code or set of computer-executableinstructions that can be employed to program a computer or otherprocessor to implement various aspects of the present invention asdiscussed above. Additionally, it should be appreciated that accordingto one aspect of this embodiment, one or more computer programs thatwhen executed perform methods of the present invention need not resideon a single computer or processor, but may be distributed in a modularfashion amongst a number of different computers or processors toimplement various aspects of the present invention.

Computer-executable instructions may be in many forms, such as programmodules, executed by one or more computers or other devices. Generally,program modules include routines, programs, objects, components, datastructures, etc. that perform particular tasks or implement particularabstract data types. Typically the functionality of the program modulesmay be combined or distributed as desired in various embodiments.

Also, data structures may be stored in computer-readable media in anysuitable form. For simplicity of illustration, data structures may beshown to have fields that are related through location in the datastructure. Such relationships may likewise be achieved by assigningstorage for the fields with locations in a computer-readable medium thatconveys relationship between the fields. However, any suitable mechanismmay be used to establish a relationship between information in fields ofa data structure, including through the use of pointers, tags or othermechanisms that establish relationship between data elements.

Various aspects of the present invention may be used alone, incombination, or in a variety of arrangements not specifically discussedin the embodiments described in the foregoing and is therefore notlimited in its application to the details and arrangement of componentsset forth in the foregoing description or illustrated in the drawings.For example, aspects described in one embodiment may be combined in anymanner with aspects described in other embodiments.

Also, the invention may be embodied as a method, of which an example hasbeen provided. The acts performed as part of the method may be orderedin any suitable way. Accordingly, embodiments may be constructed inwhich acts are performed in an order different than illustrated, whichmay include performing some acts simultaneously, even though shown assequential acts in illustrative embodiments.

Use of ordinal terms such as “first,” “second,” “third,” etc., in theclaims to modify a claim element does not by itself connote anypriority, precedence, or order of one claim element over another or thetemporal order in which acts of a method are performed, but are usedmerely as labels to distinguish one claim element having a certain namefrom another element having a same name (but for use of the ordinalterm) to distinguish the claim elements.

Also, the phraseology and terminology used herein is for the purpose ofdescription and should not be regarded as limiting. The use of“including,” “comprising,” or “having,” “containing,” “involving,” andvariations thereof herein, is meant to encompass the items listedthereafter and equivalents thereof as well as additional items.

1. A method of operating a computer comprising at least one processor,the method comprising, with the at least one processor: establishing aconnection to at least one device at an Internet Protocol (IP) layer;storing information about the at least one device obtained inconjunction with establishing the IP layer connection to the at leastone device; terminating the IP layer connection to the at least onedevice; and in response to receiving an indication of an attempt to usethe at least one device, determining presence of the at least one deviceat a non-IP layer, and reestablishing the IP layer connection to the atleast one device when the at least one device is determined to bepresent at the non-IP layer.
 2. The method of claim 1, wherein:terminating the IP layer connection to the at least one devicecomprises: determining that the IP layer connection is not active; andterminating the IP layer connection in response to the determination. 3.The method of claim 1, wherein: determining presence of the at least onedevice at the non-IP layer comprises determining presence of the atleast one device at Layer
 2. 4. The method of claim 3, wherein:determining presence of the at least one device at Layer 2 comprisesdetermining presence of the at least one device using a Layer 2 devicediscovery protocol.
 5. The method of claim 1, wherein: determiningpresence of the at least one device at the non-IP layer comprisesdetermining presence of the at least one device using a Wi-Fi Directprotocol.
 6. The method of claim 1 wherein: determining presence of theat least one device at the non-IP layer comprises indicating that the atleast one device is available for a function performed over a Layer 3connection.
 7. The method of claim 1, wherein: receiving the indicationof an attempt to use the at least one device comprises receiving, via auser interface, an input from a user indicating an attempt to use the atleast one device.
 8. The method of claim 7, wherein: receiving the inputfrom the user indicating an attempt to use the at least one devicecomprises receiving an indication to execute an application thataccesses the at least one device.
 9. The method of claim 1, wherein:establishing the IP layer connection to the at least one devicecomprises establishing the IP layer connection through an access point;and terminating the IP layer connection to the at least one devicecomprises disconnecting the at least one device from the access point.10. The method of claim 1, wherein: when the IP layer connection to theat least one device is reestablished, the method comprises communicatingwith the at least one device using a Universal Plug and Play protocol.11. The method of claim 1, further comprising: after the IP layerconnection to the at least one device has been reestablished,interacting with the at least one device to transfer data over the IPlayer connection.
 12. A wireless computing device comprising at leastone processor, the device adapted to, with the at least one processor:establish a connection to at least one device at Layer 3; storeinformation about the at least one device obtained in conjunction withestablishing the Layer 3 connection to the at least one device;terminate the Layer 3 connection to the at least one device; respond toat least one request from the at least one device for indication ofpresence of the computing device, wherein responding is performed at alayer different from Layer 3 at which the connection to the at least onedevice was established; and reestablish the Layer 3 connection to the atleast one device.
 13. The device of claim 12, wherein: the at least onerequest is generated in accordance with a Layer 2 device discoveryprotocol.
 14. The device of claim 13, wherein: responding to the atleast one request at the different layer comprises responding to the atleast one request in accordance with the Layer 2 device discoveryprotocol.
 15. The device of claim 13, wherein: the Layer 2 devicediscovery protocol comprises a Wi-Fi Direct protocol.
 16. The device ofclaim 12, further adapted to: interact with the at least one device toutilize the reestablished Layer 3 connection to the at least one devicefor data transfer.
 17. At least one computer-readable storage mediumcomprising computer-executable instructions that, when executed by atleast one processor, implement a method of monitoring a presence of atleast one device by a computer, the method comprising: establishing aconnection to at least one device at Layer 3; storing information aboutthe at least one device obtained in conjunction with establishing theLayer 3 connection to the at least one device; terminating the Layer 3connection to the at least one device; and in response to receiving anindication of an attempt to use the at least one device, determiningpresence of the at least one device at Layer 2, and reestablishing theLayer 3 connection to the at least one device based on thedetermination.
 18. The at least one computer-readable storage medium ofclaim 17, wherein: determining presence of the at least one device atLayer 2 comprises determining presence of the at least one device usinga Wi-Fi Direct protocol.
 19. The at least one computer-readable storagemedium of claim 17, wherein: receiving the indication of an attempt touse the at least one device comprises receiving, via a user interface,an input from a user indicating an attempt to use the at least onedevice.
 20. The at least one computer-readable storage medium of claim17, wherein: receiving the input from the user indicating an attempt touse the at least one device comprises receiving an indication to executean application that accesses the at least one device.